-
-
Notifications
You must be signed in to change notification settings - Fork 39
Fixes for prepared statements and literal values #1406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Footnotes
|
Hydrocharged
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
| // Value returns the literal value. | ||
| func (l *Literal) Value() any { | ||
| // LiteralValue implements the sql.LiteralExpression interface | ||
| func (l *Literal) LiteralValue() interface{} { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember way back you mentioned that we should abandon interface{} and use any now, but I've noticed you using interface{} for a few PRs now. Should we go back to interface{}?
|
Superseded by #1437 |
This PR fixes issues when using bindvars in a couple different places in certain queries. It introduces a new LiteralExpression so that it GMS and Doltgres implementations of literal values can be used interchangeably during planning and analysis.
Relies on dolthub/go-mysql-server#2946